Overview Tab

Figure: Optimization Summary - Single VM Instance

• Instance Type The current instance type, based on data collection and the recommended instance type based on the Densify analysis.
• Monthly Cost This is the per instance cost per month, for the current instance type, corresponding to the listed Catalog Instance type for on-demand usage. The second column contains the same value, for the recommended instance type.
• CPU The current CPU allocation, based on data collection and the recommended value based on the Densify analysis.
• CPU Benchmark The CPU benchmark for the current instance type and for the recommended instance type.
• Memory The current memory allocation, based on data collection and the recommended value based on the Densify analysis.

Figure: Optimization Summary - Single Instance

• Optimization Summary The specified optimization type of this instance. i.e. Downsize, Upsize, etc.
• Policy The policy used to analyze the data and generate the recommendations
• Monthly Waste Calculated as: (current estimated cost - recommended estimated cost).
• Effort The effort required to investigate and implement this recommendation.
• Instance Type The current instance type, based on data collection and the recommended instance type based on the Densify analysis.
• Group Size The current and recommended number of instances for the selected scale group.
• Avg No. of Instances The average instance count when the scale group is running for the current and recommended ASG.
• Monthly Cost This is the per instance cost per month, for the current instance type, corresponding to the listed Catalog Instance type for on-demand usage. The second column contains the same value, for the recommended instance type.
• CPU The current CPU allocation, based on data collection and the recommended value based on the Densify analysis.
• CPU Benchmark The CPU benchmark for the current instance type and for the recommended instance type.
• Memory The current memory allocation, based on data collection and the recommended value based on the Densify analysis.

• CPU Utilization (Predicted Day When Cloudex collects data and reports on it, the results are based on a ‘predicted’ day's data generated using Densify's patented analytics. This is not the average over a set sampling period, but the result of the analysis and your policy settings. Most importantly, it is based on the system's predicted modeled behavior. This is the Cloudex's machine learning.)
• CPU Utilization - Busiest Day
• Memory Utilization

• In Service Instances (for ASG and VMSS only)
• Network I/O Bytes
• Network I/O Packets

Clicking the zoom button opens the chart in a modal view with additional options to view the collected and analyzed data.

• ML Model The data is aggregated hourly for the last day (yesterday) and displayed using quartile data.
• Historical Daily The instance data, is aggregated for a single day. You can see the minimum, maximum, sustained and average values by clicking on any data point. Use the slider at the bottom to select the historical days of data to review. Up to 90 days of data is retained.

• Historical Hourly The instance data, aggregated for a single hour. Like the historical daily view, you can see the minimum, maximum, sustained and average values by clicking on any data point. Use the slider at the bottom to select the range of data to view.
• Historical (5 Min) The container's data aggregated into 5-minute samples. This option is available for CPU, Working Set Memory, RSS Memory, Total Memory, and Restarts.